Co-browsing between one or more operators and one or more visitors

ABSTRACT

Apparatuses, computer readable mediums, and methods of co-browsing between a visitor and an operator are disclosed. The method may include sending the first UI event to the visitor, receiving from the visitor a first webpage data update indicating a first update to the active tab based on the first UI event, and sending the first webpage data update to the operator, on a condition of receiving a first user interface (UI) event regarding an active tab from the operator. The method may include sending the second webpage data update to the operator indicating the update to the active tab, on a condition of receiving a second webpage data update from the visitor indicating a second update to the active tab. If updates are received from both the visitor and operator a precedence may be used to determine which to process. Updates may be used to determine an active tab.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Patent Application Nos. 61/671,593, filed on Jul. 13, 2012, and 61/810,367 filed on Apr. 10, 2013, the entire contents of both are herein incorporated by reference.

TECHNICAL FIELD

The disclosed embodiments are generally directed to co-browsing, and in particular, to co-browsing between one or more operators and one or more visitors.

BACKGROUND

Often, a visitor to a custom website needs assistance. For example, often a visitor to a custom website that offers products for sale needs help in a similar way as a visitor to a bricks and mortar store needs assistance. One way to assist the visitor is to permit an operator of the website to co-browse the website with the visitor. However, many co-browsing solutions do not provide a pleasant visitor experience. For example, often, co-browsing is achieved by sending back and forth the images of the screens of the visitor and operator, but this method often results in delays in the response time of the user interface and a degradation in the quality of the displayed screen. Additionally, often the co-browsing system will not accurately track where the visitor is in the custom website.

Therefore, there is a need in the art for an apparatus, computer readable medium, and method of multi-tab co-browsing.

SUMMARY OF EMBODIMENTS

Some disclosed embodiments provide a method of co-browsing between a visitor and an operator. The method may include sending the first user interface (UI) event to the visitor, receiving from the visitor a first webpage data update indicating a first update to the active tab based on the first UI event, and sending the first webpage data update to the operator, on a condition of receiving a first user interface (UI) event regarding an active tab from the operator. The method may include sending the second webpage data update to the operator indicating the update to the active tab, on a condition of receiving a second webpage data update from the visitor indicating a second update to the active tab.

The method may include sending to the operator an indication that the active tab is changed to a new tab, and sending the third webpage data update to the operator indicating the update to the new tab, on a condition of receiving a third webpage data update from the visitor indicating a third update to a new tab.

The method may include on a condition of receiving a second user interface (UI) event regarding a new tab from the operator, sending to the visitor an indication that the active tab is changed to the new tab, sending the second UI event to the visitor, receiving from the visitor a second webpage data update indicating a second update to the new tab based on the second UI event, and sending the second webpage data update to the operator.

The method may include adapting the first webpage data update and the second webpage data update for the operator, wherein adapting comprises adapting the first webpage data update and the second webpage data update according to a first web browsing application of the visitor to a second web browsing application of the operator.

The method may include monitoring updates to one or more tabs of the visitor; and determining an active tab of the visitor based on the monitored updates, wherein the active tab is one of the one or more tabs of the visitor. The method may include sending the operator the active tab of the visitor, on a condition of receiving an indication from the operator to co-browse with the visitor. The method may include sending at least some of the monitored updates to the one or more tabs of the visitor to the operator.

The method may include storing each of the first updates to the active tab and the second update to the active tab; and sending at least one of the stored updates to the operator, on a condition of receiving a request to replay an activity of the co-browsing.

The method may include receiving the first UI event and the second webpage data update at approximately the same time, and determining based on a precedence of the visitor and the operator whether to send the UI event to the visitor or send the second webpage data update to the operator.

In some embodiments, a method of co-browsing between a visitor and an operator is disclosed. The method may include on a condition of receiving a first webpage data update associated with a tab, updating the tab based on the first webpage data update. The method may include on a condition of receiving an event associated with the tab, sending a user interface event indicating the event, receiving a second webpage data update, and updating the tab based on the second webpage data update.

In some embodiments, the event may be generated by at least one of: a human or a co-browsing assistant module.

Some embodiments provide a computer readable non-transitory medium including instructions which when executed in a processing system cause the processing system to execute a method for multiple-tab co-browsing.

BRIEF DESCRIPTION OF THE DRAWINGS

A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings wherein:

FIG. 1 schematically illustrates a system for co-browsing, which may include mult-tab co-browsing;

FIG. 2 schematically illustrates an example of the operation of the system for multi-tab co-browsing according to some disclosed embodiments;

FIGS. 3A, 3B, and 3C schematically illustrate an example of the operation of the system for multi-tab co-browsing according to some disclosed embodiments;

FIGS. 4A and 4B illustrate a method for updating a webpage and storing webpage data updates 122;

FIG. 5 schematically illustrates the co-browsing server 102 according to some disclosed embodiments;

FIG. 6A schematically illustrates the tabs that peer A has opened in one or more web application interfaces;

FIG. 6B schematically illustrates the tabs that peer B has opened in one or more web application interfaces;

FIGS. 7A, 7B, and 7C schematically illustrate a system for multi-tab co-browsing according to some disclosed embodiments;

FIG. 8 schematically illustrates a method for multi-tab co-browsing according to some disclosed embodiments; and

FIG. 9 is a simplified functional block diagram of a computer system 900.

DETAILED DESCRIPTION OF EMBODIMENT(S)

FIG. 1 schematically illustrates a system for co-browsing 100, which may include multi-tab co-browsing. The system 100 includes a co-browsing server 102, a custom website 150, peer A 116, peer B 120, webpage updates 122, user interface (UI) events 124, requests 152, and responses 154. The co-browsing server 102 may include a UI handler 126, a web application interface 104, sender 106, listener 108, a policy engine 110, an adapter engine 112, a synchronization engine 114, and webpage data 118. Peers A 116 and B 120 may include a UI handler 126, a web application interface 104, sender 106, listener 108, a policy engine 110, an adapter engine 112, a synchronization engine 114, and webpage data 118. Peers 116, 120 and co-browsing server 102 may not include some of the functionality and modules disclosed.

Peer A 116 may send and receive webpage data updates 122 and/or UI events 124. Peer B 120 may send and receive webpage data updates 122 and/or UI events 124. The co-browsing server 102 may receive webpage updates 122 and/or UI events 124 from peer A 116 or peer B 120, and, in response, send webpage data updates 122 and/or UI events 124 to peer A 116 or peer B 120. The co-browsing server 102 may process the webpage data updates 122 and UI events 124 before sending them to peer A 116 or peer B 120.

The co-browsing server 102 may be a remote procedure call (RPC) server 102. The co-browsing server 102 may be more than one server. The functions described in relation to the co-browsing server 102 may be provided by one or more co-browsing servers 102. In some embodiments, peer A 116 and peer B 120 may send some or all of the webpage updates 122 and UI events 124 directly to one another.

Peer A 116 and peer B 120 may be computing devices. Peer A 116 and peer B 120 may be peers to one another or may have a master slave relationship. Peer A 116 and peer B 120 may be on separate computing devices or on a same computing device. A person (not illustrated) may be a user of peer A 116 or peer B 120. The user may be a visitor (not illustrated) to a custom website 150 or may be an operator (not illustrated) of the custom website 150. An operator (not illustrated) of the custom website 150 may be using either peer A 116 or peer B 120. A visitor (not illustrated) of the custom website 150 may be using either peer A 116 or peer B 120. There may be more than one peer A 116 and more than one peer B 120. In some embodiments, Peer A 116 and/or peer B 120 may include an automation module (not illustrated) that may generate events (not illustrated). For example, in some embodiments, an operator module may be included that co-browses with the visitor.

The custom website 150 may be a website running on a webserver accessible over the Internet that offers information, goods, and/or services to visitors. The custom website 150 may include the web application 156. Some examples of the web application 156 include a website of an automobile manufacture, an automotive dealer, a watch manufacturer, an educational website, a website of a local library, and a website of a broadcasting company. In some embodiments, the web application 156 may offer goods, services, or information, all of which may be for sale. The requests 152 may be requests 152 to the web application 156 from peer A 116, peer B 120, or co-browsing server 102. The responses 154 may be responses from the web application 156 to peer A 116, peer B 120, or co-browsing server 102.

The web application interface 104 may access a web application 156 where peer A 116 and peer B 120 co-browse. For example, the web application interface 104 may be Internet Explorer® (IE) or Chrome®. The web application interface 104 may render webpage data 118 in order to present webpage data 118 to the user.

The webpage data 118 may be data for a webpage such as a document object model (DOM®). The DOM® may include a DOM® application programming interface (API) (not illustrated). The webpage data 118 may include tab 128. The tab 128 may be an indication of which tab 128 of the web application interface 104 that the webpage data 118 represents.

The UI events 124 may be a user interface event recognized by the web application interface 104, or an event (not illustrated) recognized as an event by the web application interface 104. The user interface event may be performed by the visitor or the operator. The event may be an event recognized by the web application interface 104 as an event. An event may include events as defined by the World Wide Web Consortium® (W3C). Events may include UI events 124. Examples of events include a mouse click, mouse movement, a page refresh, and receipt of an event from the web application 156.

The webpage data update 122 may be an update to the webpage data 118. The webpage data update 122 may represent the difference between webpage data 118 before an event and after the event. In some embodiments, the webpage data update 122 is the difference between the current DOM and a previous DOM. The previous DOM may have been updated to the current DOM based on an event (not illustrated). The webpage data update 122 may be sent in a JavaScript Object Notation® (JSON) format, or another format. The webpage update 122 and/or the UI events 124 may include a timestamp to indicate when the update to the webpage data 118 occurred. The webpage update 122 and/or the UI events 124 may include the identification of the intended recipient of the webpage update 122 or UI events. The webpage data update 122 may include Javascript® or another script from another language that was executed on the webpage data 118 as a result of the event. The request 152 sent to the web application 150 as a result of the event may be included in the webpage data update 122. For example, a XMLHttpRequest (XHR) that resulted from the event may be included with the webpage data update 122. In some embodiments, the webpage data update 122 may include a precedence of the peer 116, 120 that sent the webpage data update 122.

The synchronization engine 114 may be configured to determine webpage data update 122 based on webpage data 118 changing as a result of an event. For example, a user may click on a button, which is an event, and the web application interface 104 may send the button click to the web application 156, which returns updates of the webpage data 118. The webpage data 118 may be updated by the web application interface 104. The synchronization engine 114 may determine the difference between the webpage data 118 before the button click and after the button click and generate webpage data update 122 that indicates the difference. The difference may be determined before the webpage data 118 is rendered by the web application interface 104 or after the webpage data 118 is rendered by the web application interface 104.

The synchronization engine 114 may be configured to take the webpage data update 122 and update the webpage data 118 to reflect the webpage data update 122. In some embodiments, the synchronization engine 114 may decode the webpage data update 122 which may be in JSON format and apply the webpage data update 122 to the webpage data 118. In some embodiments, the synchronization engine 114 uses core levels 1, 2, 3, 4, 5, or subsequent level of a DOM API. The synchronization engine 114 may be configured to discard changes to webpage data 118 when a webpage data update 122 is received from a peer 116, 120 with a higher precedence than the peer 116, 120 of the synchronization engine 114, and to make the changes to the webpage data 118 indicated in the webpage data update 122.

A peer 116, 120 or the co-browsing server 102 may be configured to determine which tab 128 a webpage data update 122 or UI events 124 is for. The peer 116, 120 or the co-browsing server 102 may be configured to determine the tab 128 based on activity of the webpage data updates 122 or UI events 124, or the webpage data update 122 or UI events 124 may indicate a tab 128.

The adapter engine 112 may be configured to adapt webpage data updates 122 and UI events 124 for a peer 116, 120 from one format to a second format. For example, webpage data updates 122 from peer A 116 may be in a format for Internet Explorer®, and the adapter engine 112 may adapt the webpage data updates 122 into a format for Chrome® for peer B 120.

The UI handler 126 may be configured to handle UI events 124 and to handle UI events 124 on peer A 116 and peer B 120. The UI handler 126 may be configured to take the UI events 124 and process the UI events 124. For example, peer A 116 may indicate that a user has selected or clicked a button in UI events 124 that is sent to the co-browsing server 102, and then sent to peer B 120. The UI handler 126 may replicate the UI events 124 for the web application interface 104 so that the web application interface 104 mirrors the selection of the button on peer A 116.

In some embodiments, the UI handler 126 will simulate the UI events 124 so that the web application interface 104 will update the webpage data 118 according to the UI events 124. The synchronization engine 114 may then determine the webpage data update 122 based on the UI events 124 and send the webpage data update 122 to the sender of the UI events 124. In this way, one peer 116, 120 may act as a master peer 116, 120 and another peer 116, 120 may act as a slave peer where the slave peer 116, 120 sends UI events 124 and receives webpage data updates 122, and the master peer 116, 120 receives UI events 124 and sends webpage data updates 122. The user of the mater peer 116, 120 may initiate events on the master peer 116, 120 and then send webpage data updates 122 based on the events.

The sender 106 may be a sockets program or a program capable of publishing peer network links that sends webpage data updates 122 and UI events 124. The sender 106 may send requests to the custom website 150. The sender 106 of peer A 116 or peer B 120 may be configured to send webpage data updates 122 and UI events 124 to peer A 116 or peer B 120 directly rather than sending the webpage data updates 122 and UI events 124 to a co-browsing server 102.

The listener 108 may be a sockets program that listens for webpage data updates 122 and UI events 124. In some embodiments, the listener 108 is a program capable of publishing peer network links that listens for webpage updates 122 and UI events 124. The listener 108 may listen for data from the web application 156.

In some embodiments, the peers 116, 120 may set up a socket communication with sender 106 and listener 108. In some embodiments, peers 116, 120 may query other peers 116, 120 for webpage data updates 122 and UI events 124. In some embodiments, peers 116, 120 may communicate 130 with one another without going through the co-browsing sever 102.

The policy engine 110 may be configured to resolve conflicts between peer A 116 and peer B 120 in co-browsing. For example, if peer A 116 and peer B 120 select different items simultaneously or approximately simultaneously or before the updates or event has been processed while co-browsing then the policy engine 110 may determine which, if either, of the selections should be sent to the other peer 116, 120. The policy engine 104 may have precedence where peer A 116 and peer B 120 are ranked. The policy engine 104 may resolve conflicts based on the precedence of peer A 116 and peer B 120.

FIG. 2 schematically illustrates an example 200 of the operation of the system for multi-tab co-browsing 100 according to some disclosed embodiments. Illustrated in FIG. 2 are web application 156, peer A 116, co-browsing server 102, and peer B 120.

The example 200 is discussed in conjunction with FIG. 1. The example 200 begins at 204 where peer A 116 may make a UI selection such as moving a mouse (not illustrated) over a button and selecting or clicking a button displayed on a webpage (not illustrated). The web application interface 104 of peer A 116 may interpret the moving of the mouse and the selection of the button. The example 200 continues at 206 where peer A 116 sends a hypertext transfer protocol (http) request 152 to the web application 156 that indicates the selection of the button. In some embodiments, the http request 152 may be a hypertext transfer protocol secure (https). The example 200 continues at 208 where the web application 156 may respond to the http request 152 that indicates the selection of the button by generating an http response 154. The example 200 continues at 210 where the web application 156 may send the http response 154 to peer A 116. The example 200 continues at 212 where the web application interface 104 of peer A 116 may integrate the http response 154 into the webpage data 118 of peer A 116. The web application interface 104 of peer A 116 may add two new buttons and remove an image as a result of the button selection. Continuing at 212, the synchronization engine 114 may determine the difference between the webpage data 118 before the selection of the button and after selection of the button. The synchronization engine 114 may generate webpage data update 122 which indicates the difference between the webpage data 118 before the selection of the button and after selection of the button. The synchronization engine 114 may determine the difference before the new webpage is rendered by the web application interface 104 of peer A 116 or after the new webpage is rendered by the web application interface 104 of peer A 116.

The example 200 continues at 214 where the peer A 116 sends the webpage data update 122 to the co-browsing server 102. The example 200 continues at 216 where the listener 108 of the co-browsing server 102 may receive the webpage data update 122. In some embodiments, the adapter engine 112 of the co-browsing server 102 may adapt the webpage data update 122 for peer B 120. For example, the web application interface 104 of peer B 120 may be IE® and the web application interface 104 of peer A 116 may be Chrome®. The adapter engine 112 of the co-browsing server 102 may adapt the webpage data update 122 from IE® to Chrome®. In some embodiments, the adapter engine 112 of the peer A 116 or peer B 120 may adapt the webpage data update 122 for peer B 120.

The example 200 continues at 218 where the co-browsing server 102 sends the webpage data update 122 to peer B 120. The example 200 continues at 220 where the listener 108 of peer B 120 may receive the webpage data update 122. The synchronization engine 114 of peer B 120 may adapt the webpage data 118 with the webpage data update 122. The web application interface 104 of peer B 120 may then render a new webpage based on the updated webpage data 118. Thus, the changes to the webpage data 118 of peer A 116 may be mirrored in the webpage data 118 of peer B 120.

The example 200 continues at 222 where a user moves a mouse of peer B 120 that moves a cursor to a different location on a screen (not illustrated) of peer B 120. The UI handler 126 generates a UI event 124 that indicates the movement of the cursor. The example 200 continues at 224 with the sender 106 of peer B sending the UI events 124 to the co-browsing server 102. The example 200 continues at 226 with the listener 108 of the co-browsing server 102 receiving the UI events 124. The co-browsing server 102 may adapt the UI events 124 for peer A 116.

The example 200 continues at 228 with the co-browsing server 102 sending the UI events 124 to peer A 116. The example 200 continues at 230 with the listener 108 of peer A 116 receiving the UI events 124. In some embodiments, peer A 116 may adapt the UI events 124 received from the co-browsing server 102 prior to applying them. The UI handler 126 of peer A 116 then may apply the UI events 124 to the webpage data 118 of peer A 116. The UI handler 126 may move the cursor (not illustrated) of peer A 116 to the same position as in peer B 120. In some embodiments, if the UI events 124 sent from peer B 120 to peer A 116 had included events that required changing the webpage data 118, such as a mouse click, then peer A 116 may implement the events in the UI events 124 and send a webpage data update 122 to peer B 120 indicating the changes in webpage data 118 as a result of UI events 124.

Thus, in the example 200 the changes made to the webpage data 118 of peer A 116 are sent to peer B 120, and UI events 124 may be sent from peer B 120 to peer A 116. In a similar fashion, peer A 116 may send UI events 124 to peer B 120, and peer B 120 may send webpage data 122 to peer A 116. In some embodiments, the operator, for example peer B 116, and visitor, for example peer A 120, may each have separate cursors so that there may be dual cursors.

Thus, peer A 116 and peer B 120 may co-browse the web application 156.

FIGS. 3A, 3B, and 3C schematically illustrate an example of the operation of the system for co-browsing 100 according to some disclosed embodiments. FIGS. 3A, 3B, and 3C schematically illustrate a webpage 302, 304, 306 of web application 156. FIG. 3A illustrates an image of a first watch 308, a cursor in a first position 310, a cursor in a second position 312, and a second watch 314. The user of the web application 156 may move the cursor from the first position 310 to the second position 312 by, for example, moving a mouse, using a touchpad, using a stylus, or by touching a touchscreen. FIG. 3B illustrates the webpage 302 after the cursor has moved from the first position 310 to the second position 312. The user then selects the first watch 308 by making a selection by, for example, clicking a mouse or touching a touchscreen or touchpad.

FIG. 3C illustrates the first watch 308, a button for selecting gold 316, and a button for selecting silver 318. After the user selects the first watch 308 in FIG. 3B, the webpage 304 is updated by deleting the second watch 314 and adding a button for selecting silver 318, and a button for selecting gold 316.

FIGS. 4A and 4B illustrate a method for updating a webpage and storing webpage data updates 122. FIGS. 4A and 4B are discussed in conjunction with FIGS. 3A, 3B, and 3C. The method 400 begins at 402 with display webpage 402. A webpage 402 may be displayed by a web application interface 104 with associated webpage data 118. For example, webpage 302 may be rendered from webpage data 118 and displayed for consumption of a user. The method 400 continues at 404 with event occurs. An event 404 has occurred. For example, a user may move the cursor from the first cursor position 310 to the second cursor position 312 (FIG. 3A). In another example, the user may make a selection as illustrated in FIG. 3B. The selection of first watch 308 may invoke one or more requests 152 and responses 154 between the peer 116, 120, and the web application 156. Moving the cursor may not require requests 152 and responses 154.

The method 400 continues at 406 with webpage data changes. For example, the webpage data 118 may be updated to indicate that the cursor position is now the second cursor position 312.

The method 400 continues at 408 with update webpage. The web application interface 104 may render a new webpage based on the webpage data change. For example, the web application interface 104 may render webpage 304 (FIG. 3B) from the updated webpage data 122 (not illustrated).

The method 400 may continue at 412 with determine webpage data update. The webpage data update 122 may be determined by, for example, peer A 116 peer B 120, or co-browsing server 102. The webpage data update 122 may be data that indicates the difference between the webpage 402 and the updated webpage 408. In some embodiments, the webpage data update 412 may be determined based on the difference between the rendered webpages, for example, webpage 302 (FIG. 3A) and webpage 304 (FIG. 3B). In some embodiments, the webpage update 412 may be determined based on the difference between the webpage data 118 and the updated webpage data (not illustrated).

The method 400 continues at 410 with “store webpage update?” The webpage data update 122 may be stored or the method 400 may return to webpage 402. It may be determined whether to store the webpage data update 122 based on how much has changed. For example, in moving the cursor from the first cursor position 310 to the second cursor position 312 many events 404 may have been received. The method 400 may aggregate the changes to the webpage data update 414 to be stored with the next webpage data update 414. The method 400 may determine whether or not how much has changed is above a threshold level. The threshold level may be a predetermined value or determined dynamically based on one or more of storage space, communication time, communication packet size, or delay times.

The method 400 may continue with store webpage data update 414 if it is determined at 410 to store the webpage data update 122. The webpage data update 122 may be associated with a tab 128 of a web application interface 104, and may store one or more events associated with the webpage data update 122 locally. In some embodiments, the webpage data update 122 may be stored by sending the webpage data update 122 to another peer 116, 120 or by sending the webpage data update 122 to the co-browsing server 102.

The method 400 may be carried out by peer A 116, peer B 120, or co-browsing server 102. In some embodiments, portions of the method 400 are carried out by peer A 116 or peer B 120, and the other portions of the method 400 are carried out by co-browsing server 102.

FIG. 4B schematically illustrates webpage data 450 being stored. The webpage data 450 may include webpage data updates 122 and initial webpage data 452. In some embodiments, a webpage data update 122 may be stored for each event 408. In some embodiments, the event 408 may be an indication of multiple events 408. In some embodiments, the webpage data update 122 may be an aggregation of the updates that occurred due to several events 408. For example, in moving a cursor across a screen the webpage 302 data update 122 may represent the entire movement of the cursor from the first position of the cursor 310 to the second position of the cursor 312. And, the event 408 may represent several events 408 of the cursor being moved across the webpage 302, or multiple events 408 may be stored. The initial webpage data 122 may be the webpage data 118 before any events 404 have occurred.

FIG. 5 schematically illustrates the co-browsing server 102 according to some disclosed embodiments. FIG. 5 illustrates peer A room 510, peer B room 550, and store and replay 575. Peer A room 510 includes tab A 632 and tab B 634. Peer B room 550 includes tab A 636, tab B 638, and tab C 640. Each of tab A 632, tab B 634, tab A 636, tab B 638, and tab C 640 may include initial webpage data 452, webpage data update 122, current webpage data 514, and UI events 124. The current webpage data 514 may be webpage data 118 that indicates the current state of the webpage.

The co-browsing server 102 may be configured to create a room for each peer 116, 120 and a tab 632, 634, 636, 638, 640 for each tab 128 that a peer 116, 120 is browsing. For example, the tabs 632, 634, 636, 638, 640 in FIG. 5 correspond to the tabs 632, 634, 636, 638, 640 in FIGS. 6A and 6B. FIG. 6A schematically illustrates the tabs 632, 634 that peer A 116 has opened in one or more web application interfaces 104. FIG. 6B schematically illustrates the tabs 636, 638, 640 that peer B 120 has opened in one or more web application interfaces 104. Peer A 116 may be currently browsing tab A 632. Peer B 120 may be currently browsing tab B 638. In some embodiments, the co-browsing web server 102 only keeps track of tabs that are being browsed from the custom website 150 or web application 156.

The co-browsing server 102 may be configured to create a room 510, 550 for a peer 116, 120 when a peer 116, 120 opens a tab 128 of custom webserver 150, and the co-browsing server 102 may be configured to create a tab 632, 634, 636, 638, 640 in the associated room 510, 550 for the tab 128 of the custom webserver 150. The co-browsing server 102 may be configured to create a tab 632, 634, 636, 638, 640 for each tab 128 of the web application 156 that the peer 116, 120 opens. The peer 116, 120 may use different web application interfaces 104.

The co-browsing server 102 may be configured to store each of the initial webpage data 452, the webpage data updates 122, the current webpage data 514, and the UI events 124. In some embodiments, the co-browsing server 102 may be configured to store all the webpage data updates 122 and UI events 124. In some embodiments, the co-browsing server 102 may be configured to store only recent webpage data updates 122 and UI events 124.

For example, peer A 116 may open tab 632 (FIG. 6A) which may be a webpage 304 (FIG. 3) or tab 128 of the custom webserver 150. Peer A 116 or the custom webserver 150 may send an indication to co-browsing server 102 that peer A 116 opened tab 632. In response, co-browsing server 102 may create peer A room 510 and tab A 632. Additionally, the co-browsing server 102 may store initial webpage data 452 which indicates the state of the tab 632 when first opened by peer A 116. The co-browsing server 102 may also store a current webpage data 514 which indicates the current state of the tab 632. The co-browsing server 102 may also store webpage data update 122 which indicate changes that are made to the tab 632. In some embodiments, every change that is made to the tab 632 is stored in the webpage data update 122 so that an operator of the web application 156 can view the browsing history of peer A 116 for tab 632.

Peer A 116 may then open tab B 634 for webpage 618. Peer A 116 or the custom webserver 150 may send an indication to co-browsing server 102 that the peer A 116 opened tab 634. In response the co-browsing server 102 may create tab B 634 in peer A room 510 with initial webpage data 122, webpage data update 122, and current webpage data 514. In a similar fashion, co-browsing server 102 may create peer B room 550, and tab A 636, tab B 638, and tab C 640.

The co-browsing server 102 may be configured to maintain a current tab 128 for each of the peers 116, 120. The co-browsing server 102 may determine a current tab for each of the peers 116, 120 based on receiving the webpage data update 122, initial webpage data 122 and current webpage data 514. The co-browsing server 102 may determine that the current tab for a peer 116, 120 is the tab 128 that last received initial webpage data 452, webpage data update 122, or current webpage data 514.

The store and replay 575 may be configured to store all or some of the webpage data updates 122 and UI events 124 and to replay the webpage data updates 122 and UI events 124. For example, an operator may request that a co-browsing web session between a visitor and operator be replayed or a web session of a visitor be replayed. The store and replay 575 may send the webpage data updates 122 and UI events 124 to the operator in so that the operator may view the co-browsing or web session. In some embodiments, the store and replay 575 may be configured to send the webpage data updates 122 and UI events 124 to the operator or visitor so that the operator or visitor can pause or speed the playing of the replaying of the web session or co-browsing session. In some embodiments, the store and replay 575 may only store and send to the visitor or operator the webpage data updates 122.

FIGS. 7A, 7B, and 7C schematically illustrate a system for co-browsing according to some disclosed embodiments. FIGS. 7A, 7B, and 7C are discussed together. Illustrated in FIG. 7A is a tab 700 of peer A 116. Illustrated in FIG. 7B is a tab 304 of peer B 120. Illustrated in FIG. 7C is co-browsing server 102, peer A 116, peer B 120, custom webserver 150, peers 775, and communications network 792.

The communications network 792 may be one or more networks including the Internet, wireless local area networks, private networks, etc. Co-browsing server 102, peer A 116, peer B 120, custom webserver 150, and peers 775 are in communicate via the communication network 792. In some embodiments, one or more of co-browsing server 102, peer A 116, peer B 120, custom webserver 150, and peers 775 may be in direct communication with one another.

FIG. 7B illustrates peer B 120 displaying tab A 632 of web application 156. The peers 775 are accessing the web application 156, but the tabs of the peers 775 are not displayed.

FIG. 7A illustrates peer A 116 displaying a tab of a web application interface 104 such Internet Explorer®. The web application interface 104 is accessing the operator web application 796. The operator web application 796 may be hosted by the co-browsing server 102, or, in some embodiments, the operator web application 796 may be hosted by another server (not illustrated). The operator web application 796 may include a co-browsing assistant 797 that may be configured to assist visitors to co-browse. For example, the co-browsing assistant 797 may generate UI events to take a visitor through a series of webpages to highlight the features of a product.

Illustrated in FIG. 7A is a visitor list 701, selected visitor information 710, a webpage control area 703, and a sales tools button 718. The visitor list 701 is a list of the visitors to the web application 156. The visitor list 701 may include information regarding the visitors. Each of the visitors may be one of the peers 775 illustrated in FIG. 7C. The information regarding the visitors may include status 730, visitor 732, and current page 734. The status 739 may indicate a current status 736. The current status 736 may indicate by a color whether the visitor is active, green, idle for a short period of time, yellow, or idle for a long period of time. In some embodiments, the status 730 may indicate whether the visitor is available for co-browsing or a likely candidate for co-browsing based on profiling the visitor for likelihood of making a purchase. In some embodiments, the status 730 may indicate whether or not the visitor is co-browsing with another operator. In some embodiments, selecting engagements 738 will provide a list of the operators that have engaged the visitor. A visitor may be a selected visitor 736. In some embodiments, additional information may be provided regarding the visitors. For example, a number of tabs that are currently opened for the web application 156 may be included for each of the visitors.

Information 710 of the selected visitor 736 may be provided by the operator web application 796. For example, the information 710 may include name, email, company, phone, location, referral source, and engagements 738. The selected visitor's name is Brad Fraiser. The engagements 738 may be a number of accepted co-browsing engagements, illustrated as “1”, and a number of rejected co-browsing engagements, illustrated as “0” or other engagement result.

The webpage control area 703 may include a time on page 726, a visits to page 724, webpage controls 722, the webpage address 720 of the co-browsed webpage 728, a co-browse button 712, a page history 714, and a page history slider 716.

The time on the page 726 may indicate the number of hours, minutes, and seconds the selected visitor 736 has been on the co-browsed webpage 728. The visits to page 724 may indicate the number of times the selected visitor 736 has visited the co-browsed page 728. For example, the visits to page 724 may indicate a number of times in the last 24 hour, illustrated as “2”, a number of times visited in the last 7 days, illustrated as “5”, a number of times in the last 30 days, illustrated as “8”, a number of times visited in the last 365 days, illustrated as “8”, and a number of times visited overall, illustrated as “9.”

The webpage controls 722 may control the co-browsed webpage 728 when co-browsing is turned on. The left arrow may go back a page in the browsing history, the right arrow may go forward a page in the browsing history, “X” may stop the loading of a webpage, and the circular arrows may reload the webpage. The co-browsed webpage 728 may be the same webpage 304 as peer B is viewing (see FIG. 7B). The co-browse button 712 may turn co-browsing on and off. In the on mode, events taken by peer A 116 will be mirrored in peer 120. In the off mode, peer A 116 observes peer B 120, also the selected visitor 736 browse the webpage application 156.

The page history 714 displays where the co-browsed webpage 728 fits into the page history 714. And peer A 116 may select a different page in the page history 714 and during co-browsing the selected page in the page history 714 will be displayed as the co-browsed webpage 728. The page history slider 716 may be used to access different pages in the page history 714.

The sales tools 718 may be a button to access sales tools for peer A 116 to use to try and sell a product or service to the selected visitor 736.

FIG. 8 schematically illustrates a method for multi-tab co-browsing according to some disclosed embodiments. The method 800 will be discussed in conjunction with FIGS. 1, 7A, 7B, and 7C. The method 800 may begin at 802 with start.

The method 800 may continue at 804 with was a user interface (UI) event received from the operator. For example, peer A 116 (FIG. 7A) may be co-browsing with peer B 120, so the co-browse button 712 would have to be switched to on. Prior to the co-browse button 712 being switched to on the operator, peer A 116, may be observing the visitor, peer B 120. The operator of peer A 116 may click the cursor 312 over the watch 308. Peer A 116 may then generate a UI events 124 that indicates the click of the cursor 312 over the watch 308. The peer A 116 may then send the UI events 124 to the co-browsing server 102.

The method 800 may continue at 806 with sending the first UI event to the visitor. For example, the co-browsing server 102 may send the UI events 124 to peer B 120. Peer B 120 may receive the UI events 124 and update the webpage data 118 (see FIG. 1) based on the UI events 124. Peer B 120 may then determine the difference between the webpage data 118 before the event in UI events 124 and after the event in UI events 124 and generate a webpage data update 122 and send the webpage update 122 to the co-browsing server 102. Note that after the click of the cursor 310 over the watch 308, the tab A would become webpage 306 (FIG. 3C).

The method 800 may continue at 808 with receiving from the visitor a webpage data update indication an update to the active tab based on the first UI event. Continuing with the example above, the webpage update 122 sent to the co-browsing server 102 indicates the update to tab A 632.

The method 800 continues at 810 with sending the first webpage data update to the operator. Continuing with the example above, the co-browsing server 102 may send the webpage update 122 to peer A 116. Peer A 116 may receive the update and update the webpage data 118 based on the webpage update 122.

The method 800 may continue at 812 with was an update received of the active tab from the visitor. If there was no update received, then method 800 may return to 804. If there was an update received of the active tab from the visitor, then the method 800 may continue at 814 with sending a webpage data update to the operator indicating the update to the active tab. Continuing with the example, the visitor at peer B 120 may now be webpage 306 and the visitor may click gold (FIG. 3C). Peer B 120 may then generate a webpage update 122 to reflect the changes in the webpage 306 after the visitor clicks gold. Peer B 120 may then generate a webpage update 122 to indicate the difference to webpage 306 after the visitor clicks gold. Peer B 120 may then send the webpage data update 122 to the co-browsing server 102. The co-browsing server 102 may adapt the webpage update 122 for peer A 116 and then send the webpage update 122 to peer A 116.

In some embodiments, an indication of the tab the webpage data update 122 regards may be sent to the operator. For example, if the visitor switches tabs, an indication of the switch may be sent to the operator. Additionally, in some embodiments, if the visitor switches tabs, webpage data may be sent to the operator for the new tab. The method 800 may end.

In some embodiments, the method 800 may include the co-browsing server 102 sending a tab to the operator. For example, the co-browsing server 102 (see FIGS. 1 and 7C) may send data to peer A 116 (FIG. 7C) of the active tab. In the example of FIGS. 7A, 7B, and 7C the active tab is tab A 632 with webpage 304 of peer B 120 (see FIG. 7B).

In some embodiments, the method 800 may include sending instructions to the first visitor to display a visitor communications area. The visitor communication area may include an area for the visitor and an area for the operator. The method 800 may include sending instructions to the operator to display an operator communication area. The operator communication area may include an area for the visitor and an area for the operator.

FIG. 9 is a simplified functional block diagram of a computer system 900. The co-browsing server 102, and the peers 116, 120 may be implemented by the computer system 900 where portion of the co-browsing server 102 and peers 116, 120 may be implemented in software, hardware, or firmware. In some embodiments, the functions of the co-browser 102 and peers 116, 120 may be distributed across multiple computer systems 900.

As illustrated in FIG. 9, the computer system 900 includes one or more processors 902, one or more memory systems 904 and one or more input/output (I/O) devices 906 in communication by two communication buses 906, 908, and a bridge 912. The communication buses 906, 908 and bridge 912 may be implemented in a variety of ways and may include one or more computer buses 908, 910 and/or bridge devices 912 as shown in FIG. 9. The I/O devices 906 can include network adapters and/or mass storage devices from which the computer system 900 can receive data from the co-browsing server 102, or the peers 116, 120 for processing by the processor 902 when the computer system 800 operates as a co-browsing server 102 or peer 116, 120.

In some embodiments, the methods and apparatuses for co-browsing between one or more operators and one or more visitors has the advantage that a proxy does not have to be used for the co-browsing since the operator and visitor may either communicate directly or through the co-browsing server 102. In some embodiments, the methods and apparatuses for co-browsing between one or more operators and one or more visitors has the advantage that software extra to the web application does not need to be installed by the operator or the visitor. In some embodiments, only extra lines of code are added to the web application of the operator and the visitor for the methods and apparatuses for co-browsing. In some embodiments, the methods and apparatuses for co-browsing between one or more operators and one or more visitors has the advantage that software extra to the web application does not need to be installed by the operator or the visitor.

The methods and apparatuses provided may be implemented in a general purpose computer, a processor, or a processor core. Suitable processors include, by way of example, a general purpose processor, a graphics processing unit (GPU), a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), and/or a state machine. Such processors may be manufactured by configuring a manufacturing process using the results of processed hardware description language (HDL) instructions and other intermediary data including netlists (such instructions capable of being stored on a computer readable media). The results of such processing may be maskworks that are then used in a semiconductor manufacturing process to manufacture a processor which implements aspects of the disclosed embodiments.

The methods or flow charts provided herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable storage medium for execution by a general purpose computer or a processor. In some embodiments, the computer-readable storage medium is a non-transitory computer-readable storage medium. Examples of computer-readable storage mediums include a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). 

What is claimed is:
 1. A method of co-browsing between a visitor and an operator, the method comprising: in response to receiving a first user interface (UI) event regarding an active tab from the operator, sending the first UI event to the visitor, receiving from the visitor a first webpage data update indicating a first update to the active tab based on the first UI event, and sending the first webpage data update to the operator; and in response to receiving a second webpage data update from the visitor indicating a second update to the active tab, sending the second webpage data update to the operator indicating the update to the active tab.
 2. The method of claim 1, further comprising: sending the active tab to the operator.
 3. The method of claim 1, further comprising: in response to receiving a third webpage data update from the visitor indicating a third update to a new tab, sending to the operator an indication that the active tab is changed to the new tab, and sending the third webpage data update to the operator indicating the update to the new tab.
 4. The method of claim 3, further comprising: sending the new tab to the operator.
 5. The method of claim 1, further comprising: in response to receiving a second user interface (UI) event regarding a new tab from the operator, sending to the visitor an indication that the active tab is changed to the new tab, sending the second UI event to the visitor, receiving from the visitor a second webpage data update indicating a second update to the new tab based on the second UI event, and sending the second webpage data update to the operator.
 6. The method of 1, further comprising: adapting the first webpage data update and the second webpage data update for the operator, wherein adapting comprises adapting the first webpage data update and the second webpage data update according to a first web browsing application of the visitor to a second web browsing application of the operator.
 7. The method of claim 1, further comprising: monitoring updates to one or more tabs of the visitor; and determining an active tab of the visitor based on the monitored updates, wherein the active tab is one of the one or more tabs of the visitor.
 8. The method of claim 7, further comprising: in response to receiving an indication from the operator to co-browse with the visitor, sending the operator the active tab of the visitor.
 9. The method of claim 7, further comprising: sending at least some of the monitored updates to the one or more tabs of the visitor to the operator.
 10. The method of claim 1, further comprising: storing each of the first update to the active tab and the second update to the active tab; and in response to a request to replay an activity of the co-browsing, sending at least one of the stored updates to the operator.
 11. The method of claim 1, wherein storing further comprises: receiving the first UI event and the second webpage data update at approximately the same time; determining based on a precedence of the visitor and the operator whether to send the UI event to the visitor or send the second webpage data update to the operator.
 12. A computer system for co-browsing between a visitor and an operator, the apparatus comprising: one or more input output devices configured to communicate over a communications network; one or more memory systems configured to store and retrieve data; and one or more processors, wherein the one or more processors are configured to: on a condition of receiving a first user interface (UI) event regarding an active tab from the operator over the one or more input output devices, send the first UI event to the visitor, receive from the visitor a first webpage data update indicating a first update to the active tab based on the first UI event, and send the first webpage data update to the operator; on a condition of receiving a second webpage data update from the visitor indicating a second update to the active tab, send the second webpage data update to the operator indicating the update to the active tab.
 13. The computer system of claim 12, wherein the one or more processors are further configured to: send the active tab to the operator.
 14. The computer system of claim 12, wherein the one or more processor are further configured to: on a condition of receiving a third webpage data update from the visitor indicating a third update to a new tab, send to the operator an indication that the active tab is changed to the new tab, and send the third webpage data update to the operator indicating the update to the new tab.
 15. The computer system of claim 14, wherein the one or more processors are further configured to: send the new tab to the operator.
 16. The computer system of claim 12, wherein the one or more processors are further configured to: on a condition of receiving a second user interface (UI) event regarding a new tab from the operator, send to the visitor an indication that the active tab is changed to the new tab, send the second UI event to the visitor, receive from the visitor a second webpage data update indicating a second update to the new tab based on the second UI event, and send the second webpage data update to the operator.
 17. The computer system of 12, wherein the one or more processor are further configured to: adapt the first webpage data update and the second webpage data update for the operator, wherein adapting comprises adapting the first webpage data update and the second webpage data update according to a first web browsing application of the visitor to a second web browsing application of the operator.
 18. The computer system of claim 12, wherein the one or more processors are further configured to: monitor updates to one or more tabs of the visitor; and determine an active tab of the visitor based on the monitored updates, wherein the active tab is one of the one or more tabs of the visitor.
 19. A method of co-browsing between a visitor and an operator, the method comprising: in response to receiving a first webpage data update associated with a tab, updating the tab based on the first webpage data update; and in response to an event associated with the tab, sending a user interface event indicating the event, receiving a second webpage data update, and updating the tab based on the second webpage data update.
 20. The method of claim 19, wherein the event is generated by at least one of: a human or a co-browsing assistant module. 